Skip to content

fix: hermes publish pipy version check#32

Merged
mateobelanger merged 3 commits into
mainfrom
fix/hermes-publish-workspace-deps
Apr 23, 2026
Merged

fix: hermes publish pipy version check#32
mateobelanger merged 3 commits into
mainfrom
fix/hermes-publish-workspace-deps

Conversation

@mateobelanger

Copy link
Copy Markdown
Member

This pull request improves the publishing workflow and documentation for the Hermes Python package. The most significant changes are a new preflight check in the publish workflow to prevent PyPI version conflicts, and the addition of a proper README.md for the PyPI landing page. These updates help ensure smoother publishing and better user guidance.

Publishing workflow improvements:

  • Added a preflight step to .github/workflows/publish-hermes-python.yml that checks if the current version of hermes-ryzome-plugin already exists on PyPI, providing a clear error and instructions if it does. This prevents confusing failures later in the workflow and helps maintainers resolve version conflicts quickly.
  • Updated the Hermes publish workflow to build workspace dependencies before running TypeScript compilation, ensuring that @ryzome-ai/ryzome-core is built before Hermes.

Documentation improvements:

  • Added a comprehensive README.md for the PyPI landing page, including installation, configuration, tool table, environment variables, and troubleshooting information. Updated pyproject.toml to point to this README so it is embedded in the sdist/wheel.

mateobelanger and others added 3 commits April 23, 2026 13:58
PyPI rejected re-uploading `hermes-ryzome-plugin 1.0.0` since it already
exists. Bumping via changeset so the next "Version Packages" PR moves
pyproject.toml to 1.0.1 (via sync-hermes-plugin-version.mjs), after which
the manual dispatch of publish-hermes-python.yml can upload cleanly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Before building anything, read the version from pyproject.toml and query
PyPI's JSON API. If the version already exists, fail immediately with a
clear message pointing at the fix (bump via changeset, merge, re-dispatch)
instead of surfacing a 400 buried at the tail of a long publish log.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@mateobelanger mateobelanger merged commit 696fa73 into main Apr 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant